I think --no-window could be a default by --script.
In the other few cases, you could use the --window option.

I think --no-window could be a default by --script.
In the other few cases, you could use the --window option.

That's a good idea, but I would leave 3.x as it is to avoid surprising changes. For 4.0 it's fine, I think.

That's a good idea, but I would leave 3.x as it is to avoid surprising changes. For 4.0 it's fine, I think.

For --gdnative-generate-json-api, etc. too.

I would keep it the same to avoid a chaos;)
You could probably print a warnig or let also the --no-window option for compatibility reasons?

FYI I've made it the default wherever it's been useful and added both options:

-	OS::get_singleton()->print("  --no-window                      Disable window creation (Windows only). Useful together with --script.\n");
+	OS::get_singleton()->print("  --window, --no-window            Run with or without opening a window. Useful with --script.\n");

Some notes:
Edit: sorry Godot seems to ignore unknown arguments;)

godot-32x --no-window -s test.gd runs a gdscript w/o window and keeps hanging...

Maybe the comment could mention that you need to explicitly call the quit() function.

-s, --script <script> Run a script.

@RandomShaper See review comments from @bruvzg, once amended this should be good to go.

Thanks!

I think --no-window could be a default by --script.
In the other few cases, you could use the --window option.

That's a good idea, but I would leave 3.x as it is to avoid surprising changes. For 4.0 it's fine, I think.

There are definitely use cases where having a Window is necessary when running with --script, like for running unit tests. See also godotengine/godot-proposals#1760.

As far as I know, it's not just a "script" which is run by Godot, it's a MainLoop derived script which just overrides the main loop implementation.

This is just to be aware if you do decide to make it a default, adding another --windowed option would be absolutely necessary.